Managing Deployment
Configuring the deployment parameters of Action Objects (AO) will define the execution start order for when the CSense Runtime Manager restarts. AOs can be configured to:
-
start in the same order in which they were originally added.
-
start in a different order to how they were originally added
-
start with delays between execution of specified AOs.
Configuring Action Object deployment
For each AO, the following properties are listed:
-
ID: the identity number of the AO in the database
-
Name: the AO name. Change the AO name by highlighting it, clicking [Edit] and retyping a new name.
-
Filename: the saved AO file pathway
-
Size: the file size of the AO
On restart, you can configure the deployment of the AOs to:
Start in the order in which they were originally added
-
This is the default option.
-
The AO listed first will start first. Remember that the size of the file will determine how long it takes to initialize and start executing.
Start in a different order
-
Use the arrows to change the execution order.
Delay Action Object deployment
-
Use the buttons at the bottom of the window to define a delay period in minutes, and then [Add], [Edit] or [Remove] the configured delay.
-
Note that the delay period will only start once all of the previous AOs have begun executing. The size of the AO file will determine how long it takes to initialize and start executing. This means that the delay is not a delay of the defined period from the Manager restart, but rather a delay from when all the previous AOs have executed.
Related topics: